Short physical uplink control channel (PUCCH) design for 5th generation (5G) new radio (NR)

ABSTRACT

A user equipment (UE) is described. The UE includes a processor and memory in electronic communication with the processor. Instructions stored in the memory are executable to acquire a first higher layer configuration indicating at least a short uplink control channel (PUCCH) resource configuration. The instructions are also executable to acquire a second higher layer configuration indicating multiple sets of PUCCH resource configurations, one set of PUCCH resource configurations within the multiple sets of PUCCH resource configurations include the short PUCCH resource configuration. The instructions are further executable to select a set of PUCCH resource configurations from the sets of PUCCH resource configurations based on a payload size of uplink control information (UCI). The instructions are additionally executable to transmit the UCI on a PUCCH resource, the PUCCH resource corresponding to a PUCCH resource configuration within the selected set of PUCCH resource configurations.

RELATED APPLICATIONS

This application is related to and claims priority from U.S. ProvisionalPatent Application No. 62/442,864, entitled “SHORT PHYSICAL UPLINKCONTROL CHANNEL (PUCCH) DESIGN FOR 5th GENERATION (5G) NEW RADIO (NR),”filed on Jan. 5, 2017, which is hereby incorporated by reference herein,in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to short physical uplinkcontrol channel (PUCCH) design for 5th generation (5G) new radio (NR).

BACKGROUND

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibilityand/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or morebase stations (gNBs) and one or more user equipments (UEs) in whichsystems and methods for short physical uplink control channel (PUCCH)design for 5th generation (5G) new radio (NR) may be implemented;

FIG. 2 is a diagram illustrating one example of a resource grid for thedownlink;

FIG. 3 is a diagram illustrating one example of a resource grid for theuplink;

FIG. 4 shows examples of several numerologies;

FIG. 5 shows examples of subframe structures for the numerologies thatare shown in FIG. 4;

FIG. 6 shows examples of slots and sub-slots;

FIG. 7 shows examples of scheduling timelines;

FIG. 8 shows examples of downlink (DL) control channel monitoringregions;

FIG. 9 shows examples of DL control channel which consists of more thanone control channel elements;

FIG. 10 shows examples of uplink (UL) control channel structures;

FIG. 11 is a block diagram illustrating one implementation of a gNB;

FIG. 12 is a block diagram illustrating one implementation of a UE;

FIG. 13 illustrates examples of short PUCCH formats;

FIG. 14 illustrates examples of reference symbol (RS) patterns for PUCCHin an Orthogonal Frequency Division Multiplexing (OFDM) symbol;

FIG. 15 illustrates an example of demodulation reference signal (DMRS)multiplexing with frequency division multiplexing (FDM) for a 1-symbolshort PUCCH;

FIG. 16 illustrates an example of RS location in a 2-symbol short PUCCHwith a discrete Fourier transform spread OFDM (DFT-S-OFDM);

FIG. 17 illustrates examples of RS pattern determination;

FIG. 18 illustrates examples of RS located in two symbols;

FIG. 19 illustrates examples of RS multiplexing of two UEs withdifferent RS patterns;

FIG. 20 illustrates examples of short PUCCH transmission with beamsweeping;

FIG. 21 illustrates various components that may be utilized in a UE;

FIG. 22 illustrates various components that may be utilized in a gNB;

FIG. 23 is a block diagram illustrating one implementation of a UE inwhich systems and methods for short PUCCH design for 5G NR operationsmay be implemented;

FIG. 24 is a block diagram illustrating one implementation of a gNB inwhich systems and methods for short PUCCH design for 5G NR operationsmay be implemented;

FIG. 25 is a flow diagram illustrating a method for implementing a shortPUCCH design for 5G NR;

FIG. 26 is a flow diagram illustrating another method for implementing ashort PUCCH design for 5G NR;

FIG. 27 is a flow diagram illustrating another method for implementing ashort PUCCH design for 5G NR; and

FIG. 28 is a flow diagram illustrating another method for implementing ashort PUCCH design for 5G NR.

DETAILED DESCRIPTION

A user equipment (UE) is described. The UE includes a processor andmemory in electronic communication with the processor. Instructionsstored in the memory are executable to acquire a first higher layerconfiguration indicating at least a short uplink control channel (PUCCH)resource configuration. The instructions are also executable to acquirea second higher layer configuration indicating multiple sets of PUCCHresource configurations, one set of PUCCH resource configurations withinthe multiple sets of PUCCH resource configurations include the shortPUCCH resource configuration. The instructions are further executable toselect a set of PUCCH resource configurations from the sets of PUCCHresource configurations based on a payload size of uplink controlinformation (UCI). The instructions are additionally executable totransmit the UCI on a PUCCH resource, the PUCCH resource correspondingto a PUCCH resource configuration within the selected set of PUCCHresource configurations.

The first higher layer configuration may include at least a number ofsymbols, a number of resource blocks (RBs), and whether frequencyhopping is applied in a case of a short PUCCH with two symbols. In thecase of the short PUCCH with two symbols, reference signal (RS)locations on the two symbols may be the same. The RS locations may beresource elements indexed with {1,4,7,10}.

A base station is also described. The base station includes a processorand memory in electronic communication with the processor. Instructionsstored in the memory are executable to send a first higher layerconfiguration indicating at least a short uplink control channel (PUCCH)resource configuration. The instructions are also executable to send asecond higher layer configuration indicating multiple sets of PUCCHresource configurations, one set of PUCCH resource configurations withinthe multiple sets of PUCCH resource configurations include the shortPUCCH resource configuration. The instructions are further executable toselect a set of PUCCH resource configurations from the sets of PUCCHresource configurations based on a payload size of uplink controlinformation (UCI). The instructions are additionally executable toreceive the UCI on a PUCCH resource, the PUCCH resource corresponding toa PUCCH resource configuration within the selected set of PUCCH resourceconfigurations.

A method for a user equipment (UE) is also described. The methodincludes acquiring a first higher layer configuration indicating atleast a short uplink control channel (PUCCH) resource configuration. Themethod also includes acquiring a second higher layer configurationindicating multiple sets of PUCCH resource configurations, one set ofPUCCH resource configurations within the multiple sets of PUCCH resourceconfigurations include the short PUCCH resource configuration. Themethod further includes selecting a set of PUCCH resource configurationsfrom the sets of PUCCH resource configurations based on a payload sizeof uplink control information (UCI). The method additionally includestransmitting the UCI on a PUCCH resource, the PUCCH resourcecorresponding to a PUCCH resource configuration within the selected setof PUCCH resource configurations.

A method for a base station is also described. The method includessending a first higher layer configuration indicating at least a shortuplink control channel (PUCCH) resource configuration. The method alsoincludes sending a second higher layer configuration indicating multiplesets of PUCCH resource configurations, one set of PUCCH resourceconfigurations within the multiple sets of PUCCH resource configurationsinclude the short PUCCH resource configuration. The method furtherincludes selecting a set of PUCCH resource configurations from the setsof PUCCH resource configurations based on a payload size of uplinkcontrol information (UCI). The method additionally includes receivingthe UCI on a PUCCH resource, the PUCCH resource corresponding to a PUCCHresource configuration within the selected set of PUCCH resourceconfigurations.

Another user equipment (UE) is described. The UE includes a processorand memory in electronic communication with the processor. Instructionsstored in the memory are executable to determine the uplink controlchannel (PUCCH) format and configuration based on a signaling from agNB. The instructions are also executable to determine the controlchannel used for uplink control information (UCI) feedback. Theinstructions are further executable to determine the resource of thecontrol channel for UCI feedback. The instructions are additionallyexecutable to transmit UCI on the selected channel.

Determining the PUCCH format and configuration may include at least ashort PUCCH format and a long PUCCH format. The short PUCCH format andlong PUCCH format may have the same or different waveforms and/ornumerologies.

A short PUCCH may be a 1-symbol short PUCCH. The 1-symbol short PUCCHmay employ a cyclic prefix Orthogonal Frequency Division Multiplexing(CP-OFDM) waveform. A format may consist of a number of resource blocks(RBs), a reference symbol (RS) pattern, and/or orthogonal sequences onRS and data symbols, and/or one or more control resource regions. The RSpattern of different UEs may be multiplexed with an orthogonal sequenceor in a frequency division multiplexing (FDM) manner.

A short PUCCH may be a 2-symbol short PUCCH. The 2-symbol short PUCCHmay employ a discrete Fourier transform spread OFDM (DFT-S-OFDM)waveform. A format may consist of a number of RBs, a RS location, and/ororthogonal sequences on RS and data symbols, and/or one or more controlresource regions. The 2-symbol short PUCCH may employ CP-OFDM waveform.A format may consist of a number of RBs, a RS pattern and location,and/or orthogonal sequences on RS and data symbols, and/or one or morecontrol resource regions.

The RS location may be the first symbol of the 2-symbol short PUCCH. TheRS location may be determined by the symbol index of a 2-symbol shortPUCCH. The RS location of the 2-symbol short PUCCH may be indicated bygNB signaling.

At least for a frequency band over 6 GHz, a UE may be configured with aset of symbols for a short PUCCH, and a short PUCCH is transmitted byselecting one symbol for a 1-symbol PUCCH and 2 symbols for a 2-symbolPUCCH within the set. The 2 symbols selected for the 2-symbol PUCCHwithin the set may be contiguous or separated within the set. Thesymbol(s) may be selected based on a gNB indication. The symbol(s) maybe selected by the UE.

Another base station (gNB) is also described. The gNB includes aprocessor and memory in electronic communication with the processor.Instructions stored in the memory are executable to determine an uplinkcontrol channel (PUCCH) format and configuration. The instructions arealso executable to receive UCI on a selected channel. A control channelused for uplink control information (UCI) feedback and a resource of thecontrol channel for UCI feedback are determined by a UE based onsignaling from the gNB.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11 and/or 12). However, thescope of the present disclosure should not be limited in this regard. Atleast some aspects of the systems and methods disclosed herein may beutilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, etc. In 3GPP specifications, a wireless communicationdevice is typically referred to as a UE. However, as the scope of thepresent disclosure should not be limited to the 3GPP standards, theterms “UE” and “wireless communication device” may be usedinterchangeably herein to mean the more general term “wirelesscommunication device.” A UE may also be more generally referred to as aterminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB) or some other similar terminology. As the scope of the disclosureshould not be limited to 3GPP standards, the terms “base station,” “NodeB,” “eNB,” and “HeNB” may be used interchangeably herein to mean themore general term “base station.” Furthermore, the term “base station”may be used to denote an access point. An access point may be anelectronic device that provides access to a network (e.g., Local AreaNetwork (LAN), the Internet, etc.) for wireless communication devices.The term “communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB may also be moregenerally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources may be indicated in the systeminformation transmitted on the downlink resources.

“Configured cells” are those cells of which the UE is aware and isallowed by an eNB to transmit or receive information. “Configuredcell(s)” may be serving cell(s). The UE may receive system informationand perform the required measurements on all configured cells.“Configured cell(s)” for a radio connection may consist of a primarycell and/or no, one, or more secondary cell(s). “Activated cells” arethose configured cells on which the UE is transmitting and receiving.That is, activated cells are those cells for which the UE monitors thephysical downlink control channel (PDCCH) and in the case of a downlinktransmission, those cells for which the UE decodes a physical downlinkshared channel (PDSCH). “Deactivated cells” are those configured cellsthat the UE is not monitoring the transmission PDCCH. It should be notedthat a “cell” may be described in terms of differing dimensions. Forexample, a “cell” may have temporal, spatial (e.g., geographical) andfrequency characteristics.

Fifth generation (5G) cellular communications (also referred to as “NewRadio”, “New Radio Access Technology” or “NR” by 3GPP) envisions the useof time/frequency/space resources to allow for enhanced mobile broadband(eMBB) communication and ultra-reliable low latency communication(URLLC) services, as well as massive machine type communication (mMTC)like services. In order for the services to use the time/frequency/spacemedium efficiently it would be useful to be able to flexibly scheduleservices on the medium so that the medium may be used as effectively aspossible, given the conflicting needs of URLLC, eMBB, and mMTC. A newradio base station may be referred to as a gNB. A gNB may also be moregenerally referred to as a base station device.

In 5G NR, at least two different types of uplink control channel (PUCCH)formats may be specified: at least one short PUCCH format and one longPUCCH format. The PUCCH channel is designed to carry uplink controlinformation (UCI). In NR, multiple short PUCCH formats may be defined,and the PUCCH format of a UE may be configured by a base station.

In NR, several PUCCH formats will be specified. For UCI, different UCImay be reported on different PUCCH channel formats. In 5G NR, bothCP-OFDM and DFT-S-OFDM waveforms are supported for UL transmission.Also, different numerologies may be used on one or more carriers orserving cells. Detailed mapping methods and signaling required for theshort PUCCH formats in NR are described. In short PUCCH designs, thelengths of 1 symbol and 2 symbols are considered. However, detailedreference symbol and control information mapping are not defined yet.Furthermore, methods to configure a PUCCH resource are not discussedyet. The systems and methods described herein detail formats for shortPUCCH design. In particular, the RS patterns, the RS location andconfigurations for a short PUCCH are described herein.

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs 160 and one or more UEs 102 in which systems and methods for shortphysical uplink control channel (PUCCH) design for 5th generation (5G)new radio (NR) may be implemented. The one or more UEs 102 communicatewith one or more gNBs 160 using one or more antennas 122 a-n. Forexample, a UE 102 transmits electromagnetic signals to the gNB 160 andreceives electromagnetic signals from the gNB 160 using the one or moreantennas 122 a-n. The gNB 160 communicates with the UE 102 using one ormore antennas 180 a-n.

The UE 102 and the gNB 160 may use one or more channels 119, 121 tocommunicate with each other. For example, a UE 102 may transmitinformation or data to the gNB 160 using one or more uplink channels121. Examples of uplink channels 121 include a PUCCH and a PUSCH, etc.The one or more gNBs 160 may also transmit information or data to theone or more UEs 102 using one or more downlink channels 119, forinstance. Examples of downlink channels 119 include a PDCCH, a PDSCH,etc. Other kinds of channels may be used.

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more transmitters 158 maytransmit signals to the gNB 160 using one or more antennas 122 a-n. Forexample, the one or more transmitters 158 may upconvert and transmit oneor more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may comprise received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) maycomprise overhead data and/or control data. For example, the secondUE-decoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include one or more of a UE short PUCCH module 126.

The UE short PUCCH module 126 may implement a short PUCCH design for 5thgeneration (5G) new radio (NR). Uplink control information and uplinkwaveform in NR are described. In LTE, the UCI carries hybrid-ARQacknowledgements (HARQ-ACK), channel state information (CSI), and ascheduling request (SR). The CSI may include one or more of channelquality indicator (CQI), rank indication (RI), precoding matrixindicator (PMI), precoding type indicator (PTI), etc. Multipledimensions of CSI may be reported from one or more cells to supportFD-MIMO and CoMP operations.

Similarly, in NR, a scheduling request (SR), if defined, needs to betransmitted outside PUSCH, as well as HARQ-ACK for latency reasons. TheCSI report in NR should be enhanced to support massive MIMO andbeamforming methods. Thus, multiple sets of CSI may be reported in NR.Again, a CSI feedback may include one or more of CQI, RI, PMI, PTI, beamindex, etc. At least two types of CSI reports may be supported, periodicCSI and aperiodic CSI. Periodic CSI report can be configuredsemi-statically. Aperiodic CSI can be trigger with a CSI request fromthe gNB 160. Therefore, physical uplink control signaling should be ableto carry at least hybrid-ARQ acknowledgements, CSI reports (possiblyincluding beamforming information), and scheduling requests.

The UCI information may be transmitted as L1/L2 control signaling (e.g.,via a physical uplink control channel (PUCCH) or physical uplink sharechannel (PUSCH) or uplink data channel). Furthermore, it should bepossible to dynamically indicate (at least in combination with RadioResource Control (RRC)) the timing between data reception and hybrid-ARQacknowledgement transmission as part of the Downlink Control Information(DCI).

In NR, different numerologies are supported on the same or differentcarriers. For the uplink transmission supports two waveform/modulationschemes based on Orthogonal Frequency Division Multiplexing (OFDM). Onewaveform/modulation scheme is cyclic prefix OFDM (CP-OFDM). Anotherwaveform/modulation scheme is discrete Fourier transform (DFT) spreadOFDM (DFT-S-OFDM), also known as single carrier FDMA (SC-FDMA), or lowPeak-to-Average Power Ratio (PAPR) waveform. Therefore, the uplinkcontrol and uplink data channel may be configured separately with thesame or different waveforms and numerologies.

LTE and 5G NR physical uplink control channel (PUCCH) are also discussedherein. In LTE, the PUCCH with normal Transmission Time Interval (TTI)length occupies a full subframe and 1 resource block (RB) for format1/2/3/5, and more than one RB is supported for Format 4. Differentformats are used to carry different number of UCI payload sizes.Frequency hopping is supported for all 1 ms TTI PUCCH formats bytransmitting two slots in two ends of the carrier frequency. The UEmultiplexing capability is performed in the frequency domain and/or timedomain depending on the PUCCH format.

Format 1/1a/1b has 3 RS symbols in each slot. Zadoff-Chu (Z-C) sequenceis used on frequency domain, orthogonal sequences are used for PUCCHspreading in time domain, N_(SF) ^(PUCCH)=4 for normal CP, N_(SF)^(PUCCH)=3 for extended CP.

Format 2/2a/2b has two RS symbols in each slot. It uses Z-C sequences onfrequency domain for UE multiplexing, no time domain multiplexing.

Format 3 has two RS symbols in each slot, it only uses time domainmultiplexing with orthogonal sequences (N_(SF) ^(PUCCH)=5 for normal CPand N_(SF) ^(PUCCH)=4 for extended CP) and no frequency domainmultiplexing.

Format 4 may occupy one or more RBs. It carries coded information bitson all data carrying symbols. Thus, it provides largest payload size,but does not support multiplexing for multiple UEs 102 in the same RB.

Format 5 uses only one RB, It has the same structure as Format 4 exceptthat a spreading factor of 2 N_(SF) ^(PUCCH)=2 is supported, thus twoUEs 102 can be multiplexed on the same RB resources.

Similar to different PUCCH formats in LTE, at least two transmissiondurations are supported for uplink control in NR. One short transmissionduration around the last OFDM symbol in a slot may be supported foruplink control in NR. This short transmission duration may be timedivision multiplexed (TDM) or frequency division multiplexed (FDM) withdata. One long transmission duration spanning multiple symbols (e.g.filling most of a slot or slots) may be frequency division multiplexed(FDM) with data.

A short PUCCH format may consist of one or two symbols. A long PUCCHformat may span multiple symbols and slots. Multiple long PUCCH formatsmay be defined (e.g., 4 symbols, a slot, and multiple slots, etc.). Along PUCCH format may be useful for larger payload HARQ-ACK feedback,CSI feedback, etc.

At least a low PAPR/CM design should be supported for the long PUCCHformat. A UCI carried by long duration UL control channel at least withlow PAPR design can be transmitted in one slot or multiple slots, andtransmission across multiple slots should allow a total duration of 1 msat least for some cases.

For PUCCH format configuration, a combination of semi-staticconfiguration and (at least for some types of UCI information) dynamicsignaling is used to determine the PUCCH formats and resources both forthe long and short PUCCH formats. The short PUCCH design is describedmore fully herein.

A short PUCCH format may occupy only 1 symbol length. In this case,CP-OFDM modulation should be used, the reference symbols and UCIcarrying symbols can be multiplexed in different subcarriers of a PUCCHresource, as shown in FIG. 13(a) for an FDM case. In case of DFT-S-OFDMwaveform, a 1 symbol short uplink control channel can be implemented bysequence based message (i.e., No RS is multiplexed in the symbol). Thenumber of orthogonal sequences limits the UE multiplexing capability andpayload sizes. For example, if the LTE Zadoff-Chu sequence is used asthe spreading sequence in an RB, a total of 12 cyclic shifts arepossible. If 2 bits can be reported by a short PUCCH, up to 3 UEs 102can be multiplexed on a single RB.

It should be noted that the sequence based 1 symbol short uplink controlchannel design can also be applied to CP-OFDM waveform. However, theUCI/RS multiplexing provides better flexibility for resource scheduling(e.g., different RS patterns) may be defined to provide different RSoverhead and multiplexing capabilities; and orthogonal sequences can beapplied in time domain or frequency domain for UCI multiplexing amongdifferent UEs 102.

A short PUCCH format may occupy two symbols. In this case, both CP-OFDMand DFT-S-OFDM modulation can be used. In case of DFT-S-OFDM, referencesymbol and the UCI carrying symbol can be TDM multiplexed, as shown inFIG. 13(b) for a TDM case.

A short PUCCH may occupy 1 symbol of reference numerology by splittingit into 2 symbols with a higher numerology (i.e., double the subcarrierspacing and reduce the symbol length by half), as shown in FIG. 13(c)for a TDM with symbol splitting case. This 1-symbol design is actually a2-symbol design with a higher numerology, and the same design as2-symbol PUCCH can be used.

Furthermore, in order to support TDM of short PUCCH from different UEs102 in the same slot, a mechanism to tell the UE 102 in which symbol(s)in a slot to transmit the short PUCCH on is supported at least above 6GHz. The OFDM symbols for the short uplink control channel may not belimited to the last 1 or 2 symbols in a slot. In other words, theearlier symbols and/or the symbols at the beginning of a slot may alsobe signaled as the uplink control channel.

The 1-symbol short PUCCH formats are described herein. A short PUCCH issuitable for a small number of HARQ-ACK bits and/or SR. For a small UCIpayload, the channel coding method of UCI carried on a short uplinkcontrol channel, polar code may not be used, and repetition/spreadingcode and/or linear block code can be used. Even within short PUCCH,different payload sizes may be supported, and multiple formats orconfigurations may be supported. Several approaches are considered tocarry UCI on a 1-symbol PUCCH.

One approach may be a sequence-based PUCCH. In this approach, no RS isused, and PUCCH is transmitted based on sequences. Each sequence mayindicate one state. For sequence-based 1-symbol PUCCH, both DFT-S-OFDMand CP-OFDM may be used. Especially, if DFT-S-OFDM is used, the LTEZadoff-Chu sequence may be reused to achieve UE multiplexing and UCIpayload.

The UE multiplexing capability may be limited by the total number oforthogonal sequences. For example, if LTE length 12 Z-C sequences areused as the sequence, there are 12 orthogonal sequences available bycyclic shift. Thus, different UE multiplexing and UCI payload may besupported by different sequence set allocations. If 1 bit of UCI isreported, each UE 102 may be assigned with two sequences, thus an RB canbe multiplexed by up to 6 different UEs 102. If 2 bits of UCI arereported, each UE 102 may be assigned with four sequences, thus an RBcan be multiplexed by up to 3 different UEs 102.

Furthermore, a short PUCCH may occupy multiple RBs especially if UEmultiplexing is supported. In this case, the orthogonal sequence can bedesigned based on the total number of REs. Thus, different UEmultiplexing capability and UCI payload sizes can be supportedaccordingly. To provide frequency diversity, separate PUCCH regions orsubbands should be configured for a UE 102, and the PUCCH can betransmitted simultaneously in both regions/subbands.

To summarize, for a sequence based 1-symbol short PUCCH, one or more ofthe following parameters should be specified: the number of RBs in aPUCCH region/subband; the orthogonal sequence set of the PUCCH resource;the orthogonal sequence subset assign to the given UE 102; and thefrequency diversity with multiple PUCCH regions/subbands.

Another approach to carry UCI on a 1-symbol PUCCH is an RS and UCImultiplexing-based PUCCH. In this approach UCI and RS multiplexing canbe used. In this case, CP-OFDM modulation should be used for 1-symbolPUCCH. The reference symbols (RS) and UCI carrying symbols can bemultiplexed in different subcarriers of a PUCCH resource. The RS and UCImultiplexing is more flexible to support different UE multiplexingcapabilities and UCI sizes.

RS pattern design is described herein. Several designs can be consideredfor reference signals/symbols location and information bit mapping. Someexamples include 2 RS in each RB, 3 RS in each RB, 4 RS in each RB, and6 RS in each RB. FIG. 14 shows the reference signal pattern designs. Foreach RS setting, at least two patterns can be defined, denoted aspattern 1 and pattern 2 without loss of generality.

The number of RS in each RB is a tradeoff between the DMRS reliability,the multiplexing capability and UCI payload size. A higher number of RSprovides better demodulation accuracy and UE multiplexing capability,but reduces the number of symbols for UCI payload, which, thus, supportsa lower payload size.

Multiplexing capabilities for an RS and UCI multiplexing-based PUCCH arealso described herein. For a short PUCCH, in one method, UE multiplexingis not supported. FDM may be used for different UEs 102 so that theshort PUCCH resources of different UEs 102 do not overlap with eachother. However, this kind of dedicated resource for each UE 102 causeswaste of resources since PUCCH is not always transmitted.

In another approach, UE multiplexing for PUCCH is supported to share thesame RB resources for different UEs 102. To separate the signals fromdifferent UEs 102 multiplexed on the same RB, some orthogonal codeshould be applied on the RS and/or UCI data symbols. Several examples oforthogonal sequences with different spreading factors are listed inTables 1-3 below. Table 1 is for a spreading factor of 2. Table 2 is fora spreading factor of 3. Table 3 is for a spreading factor of 4.

TABLE 1 Orthogonal sequence index n_(OC) Orthogonal sequences 0 [+1 +1]1 [+1 −1]

TABLE 2 Orthogonal sequence index n_(OC) Orthogonal sequences 0 [1 1 1]1 [1 e^(j2π/3) e^(j4π/3)] 2 [1 e^(j4π/3) e^(j2π/3)]

TABLE 3 Orthogonal sequence index n_(OC) Orthogonal sequences 0 [+1 +1+1 +1] 1 [+1 −1 +1 −1] 2 [+1 +1 −1 −1] 3 [+1 −1 −1 +1]

Furthermore, a short PUCCH may occupy multiple RBs especially if UEmultiplexing is supported. In this case, the orthogonal sequence for RScan be designed based on the total number of RS symbols. For example,the LTE Zadoff-Chu (ZC) sequences and cyclic shifts can be reused fortotal number of RS has the length of 12 or multiples of 12.

The number of orthogonal sequences applied to RS and UCI data symbolsjointly determine the UE multiplexing capability. The total number ofUCI data symbols and the spreading factor determines the number ofinformation bits that can be carried on a PUCCH. Thus, many differentcombinations of RS pattern and spreading factors on RS and UCI carryingsymbols can be considered. Each combination may target for a specificmaximum UCI bits.

Another method of DMRS pattern multiplexing for different UEs 102 can beachieved by applying different DMRS patterns for different UEs 102. Inthis case, the UCI data should not be allocated to REs reserved for DMRSof other UEs 102 as well. Thus, there is no interference on the DMRSfrom other UEs 102. FIG. 15 shows an example of RS multiplexing of 2 UEs102 with different RS patterns. Orthogonal sequences can still beapplied on the REs carrying coded UCI data.

Frequency hopping support for an RS and UCI multiplexing-based PUCCH arealso described herein. To provide frequency diversity, separate PUCCHregions or subbands should be configured for a UE 102, and the PUCCH canbe transmitted simultaneously in both regions/subbands. As a summary,for a 1-symbol short PUCCH based on RS and UCI multiplexing, thefollowing parameters should be specified: the number of RBs in a PUCCHregion/subband; the RS pattern and spreading sequence if applied; thespreading sequence on UCI data symbols if applied; and the frequencydiversity with multiple PUCCH regions/subbands.

2-symbol short PUCCH formats are also described herein. For a 2-symbolshort PUCCH format in NR, both CP-OFDM and DFT-S-OFDM can be used.However, it may be more appropriate to use DFT-S-OFDM based short PUCCHfor its lower PAPR properties.

DFT-S-OFDM based 2-symbol short PUCCH are described herein. In the caseof a DFT-S-OFDM waveform, the RS pattern and UCI information bit can bemultiplexed in TDM manner (i.e., one symbol is used to carry DMRS; theother symbol is used for coded UCI information bits). LTE Zadoff-Chu(ZC) sequences and cyclic shifts can be reused for the DMRS pattern. Forthe RS and information bit multiplexing, several methods can beconsidered for the mapping.

In a first method, the first symbol is always DMRS, and the secondsymbol is always for UCI data. The DMRS is transmitted first so that thebase station (gNB 160) can decode earlier compared with a post-loadedDMRS, as shown in FIG. 16(a). However, if different UEs 102 start shortPUCCH at different symbols, the DMRS pattern of one UE 102 may collidewith the UCI data part of another UE 102. This may cause interference tothe Z-C sequence used for DMRS.

In a second method, to avoid interference due to RS misalignment amongUEs 102, the location of the DMRS may be fixed in certain symbollocations. For example, in FIG. 16(b), a symbol with odd symbol index isused for DMRS, a symbol with even symbol index is used for UCI data, orvice versa. Therefore, depending on the starting symbol of a 2-symbolshort PUCCH, the DMRS location may be in the first symbol of secondsymbol of a 2-symbol PUCCH.

In a third method, the RS location is changeable or configurable. The RSlocation within a 2-symbol PUCCH can be semi-statically configured byhigher layer signaling for a given UE 102. The RS location within a2-symbol PUCCH can be dynamically indicated by a DCI. The adjustable RSlocation can be used to avoid interference due to RS misalignment amongdifferent UEs 102.

Furthermore, a short PUCCH may occupy multiple RBs especially if UEmultiplexing is supported. The number of orthogonal sequences applied toRS and UCI data symbols jointly determine the UE multiplexingcapability. The total number of UCI data symbols and the spreadingfactor determines the number of information bits that can be carried ona PUCCH. Thus, many different combinations of RS pattern and spreadingfactors on RS and UCI carrying symbols can be considered. Eachcombination may target for a specific maximum UCI bits.

To provide frequency diversity, frequency hopping of a 2-symbol shortPUCCH can be configured. In this case, separate PUCCH regions orsubbands should be configured for a UE 102, and the PUCCH can betransmitted simultaneously in both regions/subbands.

If frequency diversity is supported for a DFT-S-OFDM based 2-symbolshort PUCCH different approaches may be used for DMRS location. In oneapproach, the DMRS location of the PUCCH transmission in different PUCCHregions or subbands can be switched (i.e., if the RS is located in thefirst symbol in a first PUCCH region, the RS should be located in thesecond symbol in the second PUCCH region for frequency diversity). Inanother approach, the DMRS location of the PUCCH transmission indifferent PUCCH regions or subbands can be the same.

A CP-OFDM based 2-symbol short PUCCH is also described herein. In thecase of a CP-OFDM waveform, the RS pattern in a symbol can be based onthe RS pattern defined for 1-symbol PUCCH above. Several methods can beconsidered for the RS and UCI symbol multiplexing.

In a first method (Method 1), RS is located in the first symbol only.Front load RS has the advantage of fast decoding. With RS in the firstsymbol only also reduces the RS overhead, and more REs can be used tocarry coded UCI symbols. Within this method, several approaches can beused to determine the RS pattern.

In one approach, a fixed RS pattern in always applied. For example, inFIG. 17(a) with 3 RS in a RB, pattern 1 is always applied. In anotherapproach, the RS pattern is determined based on the symbol index of thestarting symbol. For example, in FIG. 17(b) with 3 RS in a RB, pattern 1is used if the starting symbol has an even index number, and pattern 2is used if the starting symbol has an odd index number, or vice versa.In yet another approach, the RS pattern can be changeable orconfigurable. The RS pattern can be semi-statically configured by higherlayer signaling or dynamically indicated by a DCI for a given UE 102.

In a second method (Method 2), RS is located in both symbols. RS in bothsymbols provides better demodulation accuracy. Within this method,several approaches can be used to determine the RS pattern.

In one approach, the same pattern is applied to both symbols, as shownin FIG. 18(a). The RS pattern can be fixed, or semi-staticallyconfigured by higher layer signaling, or dynamically indicated by a DCIfor a given UE 102. In another approach, different RS patterns are usedin different symbols, as in FIG. 18(b). An interlaced pattern is used indifferent symbols. The RS pattern on a symbol may be configuredsemi-statically. The RS pattern on a symbol may be indicated by a basedstation via a DCI. The RS pattern may be determined based on the symbolindex of the given symbol (e.g., pattern 1 is used for symbol with evenindex number, and pattern 2 is used for symbol with odd index number, orvice versa).

In a third method (Method 3), the RS location is changeable orconfigurable. With this method, the RS is only available in one symbol.But the RS may be in the first symbol or the second symbol of a 2-symbolshort PUCCH. The RS location within a 2-symbol PUCCH can besemi-statically configured by higher layer signaling for a given UE 102.The RS location within a 2-symbol PUCCH can be dynamically indicated bya DCI. The same approaches as in Method 1 can be applied to Method 3 forthe RS pattern selection on the RS carrying symbol.

Furthermore, a short PUCCH may occupy multiple RBs especially if UEmultiplexing is supported. The number of orthogonal sequences applied toRS and UCI data symbols jointly determine the UE multiplexingcapability. The total number of UCI data symbols and the spreadingfactor determines the number of information bits that can be carried ona PUCCH. Thus, many different combinations of RS pattern and spreadingfactors on RS and UCI carrying symbols can be considered. Eachcombination may target for a specific maximum UCI bits.

Another method of DMRS pattern multiplexing for different UEs 102 can beachieved by applying different DMRS patterns for different UEs 102. Inthis case, the UCI data should not be allocated to REs reserved for DMRSof other UEs 102 as well. Thus, there is no interference on the DMRSfrom other UEs 102. FIG. 19 shows an example of RS multiplexing of 2 UEs102 with different RS patterns. Orthogonal sequences can still beapplied on the REs carrying coded UCI data. The RS multiplexing ofdifferent UEs may be allocated in the same symbol as in FIG. 19(a), orin different symbols as in FIG. 19(b).

To provide frequency diversity, frequency hopping of a 2-symbol shortPUCCH can be configured. In this case, separate PUCCH regions orsubbands should be configured for a UE 102, and the PUCCH can betransmitted simultaneously in both regions/subbands. If frequencydiversity is supported for a CP-OFDM based 2-symbol short PUCCH,different approaches may be used for DMRS location. In one approach, theDMRS location of the PUCCH transmission in different PUCCH regions orsubbands can be switched (i.e., if the RS is located in the first symbolin a first PUCCH region, the RS should be located in the second symbolin the second PUCCH region for frequency diversity). In anotherapproach, the DMRS location of the PUCCH transmission in different PUCCHregions or subbands can be the same.

As a summary, for a 2-symbol short PUCCH resource, one or more of thefollowing parameters should be specified: the waveform (e.g., CP-OFDM orDFT-S-OFDM); the number of RBs in a PUCCH region/subband; the RS patternand spreading sequence if applied; the RS location; the spreadingsequence on UCI data symbols if applied; and the frequency diversitywith multiple PUCCH regions/subbands.

Configuration of a short PUCCH is also described herein. In LTE,multiple PUCCH formats are defined for different maximum payload sizes.Similarly in NR, multiple short PUCCH formats should be configured fordifferent maximum payload sizes. Even if short PUCCH is designed forHARQ-ACK and SR only, the payload sizes may be different for differentuse cases. For example, ultra-reliable low latency communication (URLLC)traffic may need only 1 bit of HARQ-ACK, but feedback for eMBB trafficmay require more HARQ-ACK bits. Thus, tradeoffs between RS, informationbits and multiplexing capabilities should be considered.

Furthermore, for a given PUCCH format, the resource allocation can bemore flexible than LTE depending on the channel conditions. For UEs 102with very good signal condition, fewer RB resources may be allocated fora PUCCH. For UEs 102 with bad signal conditions (e.g., cell edge UEs102), more RB resources may be allocated for a PUCCH.

Therefore, for a short PUCCH, at least the following parameters may beconfigured for a given UE 102: the number of symbols for the PUCCH; thewaveform (e.g., CP-OFDM or DFT-S-OFDM); the number of RBs in a PUCCHregion/subband; the RS pattern and spreading sequence if applied; the RSlocation for 2-symbol PUCCH; the spreading sequence on UCI data symbolsif applied; and the frequency diversity with multiple PUCCHregions/subbands. In order to reduce the signaling overhead, a list ofsupported short uplink control channel formats can be specified, eachwith a given set of parameters, and the name or index of a support shortPUCCH format is indicated or configured to a UE 102.

Moreover, the 5G NR supports different frequency bands with differentchannel characteristics. Thus, the PUCCH behavior may be different fordifferent frequency bands. For below 6 GHz frequency bands, the channelcondition is more stable. Thus, it is better to use a semi-staticconfigured PUCCH resource, or a dynamic indicated PUCCH resource. Forfrequency band above 6 GHz, beamforming technology is critical for theoperation. Considering beam sweeping, a UE 102 may use different beamsin different symbols.

Therefore, for a frequency band above 6 GHz, a one symbol short PUCCHmay be configured with multiple symbols. Each symbol may use the same ordifferent beams from other symbols. The UE 102 may transmit PUCCH in oneof the symbols among the configured symbols, as shown in FIG. 20(a).

For a frequency band above 6 GHz, a two symbol short PUCCH may beconfigured with multiple symbols. The UE 102 may transmit PUCCH in twoof the symbols among the configured symbols. In one approach, a 2-symbolshort PUCCH can be transmitted in any two consecutive symbols within theconfigured PUCCH symbols, as shown in FIG. 20(b). In another approach, a2-symbol short PUCCH can be transmitted in any two symbols within theconfigured PUCCH symbols, as shown in FIG. 20(c).

If a CP-OFDM waveform is used for a 2-symbol short PUCCH, the beam inone symbol may be the same or different from the other symbol. Thus, itis better to have DMRS in both 2 symbols. If a DFT-S-OFDM waveform isused for a 2-symbol short PUCCH, the beam of two symbols in the shortPUCCH should be the same. Also, if DFT-S-OFDM waveform is used for a2-symbol short PUCCH, it may be better to use consecutive 2 symbols withthe same beam.

For both 1-symbol and 2-symbol short PUCCH above the 6 GHz frequencyband, in one method, the gNB 160 may indicate which symbols and/or beamsshould be used for short PUCCH transmission by dynamic signaling viaDCI. In another method, the UE 102 may choose the symbols and/or beamsfor the short PUCCH transmission.

To determine the short PUCCH resource, 5G NR requires moreconfigurations. At least one of the following aspects may be supportedin NR.

In a first aspect, a short PUCCH format and/or resource for a UE 102 canbe semi-statically configured by higher layer signaling. If a UE 102 isnot configured for a short PUCCH format and/or resource by higher layersignaling, the UE 102 may use a long PUCCH format. If a UE 102 isconfigured for a short PUCCH format and/or resource by higher layersignaling, the UE 102 may use a short PUCCH format. Alternatively, if aUE 102 is not configured with a long PUCCH format and/or resource byhigher layer signaling, the UE 102 may use a short PUCCH format. If a UE102 is configured with a long PUCCH format and/or resource by higherlayer signaling, the UE 102 may use a long PUCCH format.

In another aspect, a short PUCCH format and/or resource for a UE 102 canbe dynamically indicated by physical layer signaling (e.g., a DCI). TheDCI format may have an n-bit information field indicating the PUCCHformat irrespective of RRC configuration. Alternatively, the DCI formatmay have the n-bit information field if the UE 102 is configured withsome configuration (e.g., a configuration of short PUCCH format, aconfiguration of a certain transmission mode/scheme, a configuration ofLicense-assisted-access (LAA) cell, etc.) by higher layer signaling, andthe DCI format may not have the n-bit information field otherwise. TheDCI formats related to system information, paging and/or random accessresponse may not have the n-bit information field, and the other DCIformats (e.g., DCI formats related to user-specific payload) may havethe n-bit information field.

In another aspect, a short PUCCH format and/or resource for a UE 102 canbe adaptively determined based on the UCI types and/or the number of UCIbits. If UCI types are HARQ-ACK or SR only, a short PUCCH format may beused. A short PUCCH format may be used if the UCI payload is smaller orequal to a threshold (e.g., 4 bits or 8 bits). Different short PUCCHconfigurations may be used for different payload sizes. A long PUCCHformat may be used if the UCI payload size is greater than thethreshold.

In another aspect, a short PUCCH format and/or resource for a UE 102 canbe adaptively determined based on the DL transmission mode or DLtransmission scheme which may be configured by higher layer signaling.

In yet another aspect, different short PUCCH formats may be configuredor utilized for different types of traffic.

PUCCH considerations for ultra-reliable low latency communications(URLLC) are also described herein. For URLLC traffic, several aspectsneed to be considered for PUCCH design and PUCCH transmissions.

One aspect is HARQ-ACK feedback for a downlink URLLC transmission. URLLCtraffic requires ultra-reliability and low latency. The HARQ-ACK forURLLC packet should be supported to provide the required reliability.Furthermore, the HARQ-ACK feedback should be reported immediately aftera URLLC transmission. Moreover, the HARQ-ACK feedback should have thesame or higher reliability than the URLLC data transmission (i.e., thecurrent PUCCH channel Bit Error Rate (BER) requirements of 1% or 0.1%cannot satisfy the URLLC requirements). The HARQ-ACK BER requirementshould be the same as or better than the URLLC data channel (i.e., atleast 10{circumflex over ( )}-5 or 10{circumflex over ( )}-6 or evenlower).

Thus, the PUCCH format for URLLC DL transmission should also provideultra-reliability and low latency after a URLLC DL transmission. Onlyshort PUCCH should be used for URLLC HARQ-ACK feedback. The position ofshort PUCCH can be determined dynamically based on URLLC DL datatransmission (e.g., immediately after a URLLC DL transmission with a1-symbol gap period). The URLLC traffic may be defined with aself-contained slot structure, and PUCCH is reserved at the end of theself-contained slot.

In a design of HARQ-ACK feedback for URLLC, the following aspects can betargeted. URLLC short control channel should be more robust (e.g.,BER<10{circumflex over ( )}-6). Only 1 or 2 HARQ-ACK bits may besupported. Only 1 HARQ process may be supported. For example, multipleRBs may be used for a URLLC control feedback. Frequency diversity andtransmit diversity can be applied.

To minimize the delay, one symbol short PUCCH may be used for feedbackof a URLLC DL transmission. Furthermore, two symbol short PUCCH may beused for better reliability. If multiplexing of RS and UCI is used, theRS pattern may be different from other PUCCH. For example, 6 RS and 6data symbols may be in each RB. Longer orthogonal cover code (OCC) maybe used.

A sequence-based short PUCCH may be used. Thus, a UE 102 may beconfigured with a set of sequences across the configured RB resourcesfor the URLLC short PUCCH. The feedback HARQ-ACK or SR bits may bemapped to different sequences in the set.

URLLC short PUCCH may use a different numerology from other short PUCCH.Specifically, the URLLC PUCCH should have shorter symbol lengths thanother short PUCCH or PUSCH transmissions.

Thus, based on these aspects, a short PUCCH for URLLC may be configuredwith a different set of parameters for a UE 102. The format of a shortPUCCH for URLLC traffic may be semi-statically configured by higherlayer signaling. The resource and location of short PUCCH may besemi-statically configured or implicitly mapped based on URLLC DLtransmission. The short PUCCH for URLLC feedback should be dynamicallytransmitted based on DL URLLC reception.

As mentioned, URLLC traffic requires ultra-reliability and low latency,and may collide with a PUCCH or PUSCH transmission of the same UE 102.As a general rule, the URLLC traffic should have higher priority thanany other UL transmissions. In the case where a short PUCCH transmissioncollides with a URLLC traffic in the same symbol, the URLLC should havehigher priority. Several methods can be considered.

In a first method (Method 1), URLLC is transmitted and the PUCCH in theoverlapping symbol is dropped. This is a simple solution and can beapplicable in all cases regardless of PUCCH waveforms and/ornumerologies. The whole short PUCCH should be dropped for a 1-symbolPUCCH. For a 2-symbol PUCCH, if the URLLC collides with the first symbolof a short PUCCH, all short PUCCH symbols should be dropped. If a2-symbol short PUCCH transmission already starts, and the URLLC collideswith the 2nd symbol in a 2-symbol short PUCCH, the second symbol of theshort PUCCH is dropped.

In a second method (Method 2), simultaneous transmission of URLLC andshort PUCCH, with power scaling on short PUCCH REs may be performed. Ifsimultaneous transmission of URLLC and PUCCH is supported on the samesymbol, UL transmit power should be allocated to the URLLC trafficfirst. The remaining power can be power scaled on the PUCCH REs in thesame UL symbol. In one approach, in the case of overlapping REs betweenURLLC and PUSCH, the URLLC signals are transmitted and PUCCH symbols oncorresponding REs are dropped. In another approach, in the case ofoverlapping REs between URLLC and PUSCH, the URLLC signals aretransmitted and the entire PUCCH symbol should be dropped as inmethod 1. Note that if URLLC traffic and PUCCH uses different waveforms,simultaneous transmission of URLLC and PUCCH may not be possible. Also,if URLLC traffic and PUCCH uses different numerologies, some guardinterval may be required between different numerologies, andsimultaneous transmission of URLLC and PUCCH may not be supported insome cases.

The URLLC UL transmission may be scheduled or pre-configured with aresource known to the gNB 160. The gNB 160 may blind decode the URLLCtraffic and handle the other channels (e.g., PUCCH and PUSCH based onthe specified or configured UE behavior). On the other hand, it isbeneficial for a UE 102 to indicate a URLLC UL transmission to the gNB160. The indication may be a short URLLC PUCCH that is transmittedsimultaneously with URLLC PUSCH data. The short URLLC PUCCH resource maybe configured semi-statically as an SR resource. The PUCCH format designmay be the same as the PUCCH for HARQ-ACK feedback of a DL URLLCtransmission.

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the data 146 and/or other information 142 may involve errordetection and/or correction coding, mapping data to space, time and/orfrequency resources for transmission, multiplexing, etc. The encoder 150may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more antennas 180 a-n. For example, thereceiver 178 may receive and downconvert signals to produce one or morereceived signals 174. The one or more received signals 174 may beprovided to a demodulator 172. The one or more transmitters 117 maytransmit signals to the UE 102 using one or more antennas 180 a-n. Forexample, the one or more transmitters 117 may upconvert and transmit oneor more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may comprise received payload data, which may be stored in adata buffer 162. A second eNB-decoded signal 168 may comprise overheaddata and/or control data. For example, the second eNB-decoded signal 168may provide data (e.g., PDSCH HARQ-ACK information) that may be used bythe gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include one or more of a gNB short PUCCH module 194. The gNB shortPUCCH module 194 may implement a short PUCCH design for 5G NR asdescribed herein.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the data 105 and/or otherinformation included in the information 101 may involve error detectionand/or correction coding, mapping data to space, time and/or frequencyresources for transmission, multiplexing, etc. The encoder 109 mayprovide encoded data 111 to the modulator 113. The transmission data 105may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialsubframe.

It should also be noted that one or more of the elements or partsthereof included in the eNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

FIG. 2 is a diagram illustrating one example of a resource grid for thedownlink. The resource grid illustrated in FIG. 2 may be utilized insome implementations of the systems and methods disclosed herein. Moredetail regarding the resource grid is given in connection with FIG. 1.

In FIG. 2, one downlink subframe 269 may include two downlink slots 283.N^(DL) _(RB) is downlink bandwidth configuration of the serving cell,expressed in multiples of N^(RB) _(sc), where N^(RB) _(sc) is a resourceblock 289 size in the frequency domain expressed as a number ofsubcarriers, and N^(DL) _(symb) is the number of OFDM symbols 287 in adownlink slot 283. A resource block 289 may include a number of resourceelements (RE) 291.

For a PCell, N^(DL) _(RB) is broadcast as a part of system information.For an SCell (including an LAA SCell), N^(DL) _(RB) is configured by aRRC message dedicated to a UE 102. For PDSCH mapping, the available RE291 may be the RE 291 whose index 1 fulfils 1≥1_(data,start) and/or1_(data,end)≥1 in a subframe.

In the downlink, the OFDM access scheme with cyclic prefix (CP) may beemployed, which may be also referred to as CP-OFDM. In the downlink,PDCCH, EPDCCH, PDSCH and the like may be transmitted. A downlink radioframe may consist of multiple pairs of downlink resource blocks (RBs)which is also referred to as physical resource blocks (PRBs). Thedownlink RB pair is a unit for assigning downlink radio resources,defined by a predetermined bandwidth (RB bandwidth) and a time slot. Thedownlink RB pair consists of two downlink RBs that are continuous in thetime domain.

The downlink RB consists of twelve sub-carriers in frequency domain andseven (for normal CP) or six (for extended CP) OFDM symbols in timedomain. A region defined by one sub-carrier in frequency domain and oneOFDM symbol in time domain is referred to as a resource element (RE) andis uniquely identified by the index pair (k,l) in a slot, where k and lare indices in the frequency and time domains, respectively. Whiledownlink subframes in one component carrier (CC) are discussed herein,downlink subframes are defined for each CC and downlink subframes aresubstantially in synchronization with each other among CCs.

FIG. 3 is a diagram illustrating one example of a resource grid for theuplink. The resource grid illustrated in FIG. 3 may be utilized in someimplementations of the systems and methods disclosed herein. More detailregarding the resource grid is given in connection with FIG. 1.

In FIG. 3, one uplink subframe 369 may include two uplink slots 383.N^(UL) _(RB) is uplink bandwidth configuration of the serving cell,expressed in multiples of N^(RB) _(sc), where N^(RB) _(sc) is a resourceblock 389 size in the frequency domain expressed as a number ofsubcarriers, and N^(UL) _(symb) is the number of SC-FDMA symbols 393 inan uplink slot 383. A resource block 389 may include a number ofresource elements (RE) 391.

For a PCell, N^(UL) _(RB) is broadcast as a part of system information.For an SCell (including an LAA SCell), N^(UL) _(RB) is configured by aRRC message dedicated to a UE 102.

In the uplink, in addition to CP-OFDM, a Single-Carrier FrequencyDivision Multiple Access (SC-FDMA) access scheme may be employed, whichis also referred to as Discrete Fourier Transform-Spreading OFDM(DFT-S-OFDM). In the uplink, PUCCH, PDSCH, PRACH and the like may betransmitted. An uplink radio frame may consist of multiple pairs ofuplink resource blocks. The uplink RB pair is a unit for assigninguplink radio resources, defined by a predetermined bandwidth (RBbandwidth) and a time slot. The uplink RB pair consists of two uplinkRBs that are continuous in the time domain.

The uplink RB may consist of twelve sub-carriers in frequency domain andseven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbolsin time domain. A region defined by one sub-carrier in the frequencydomain and one OFDM/DFT-S-OFDM symbol in the time domain is referred toas a RE and is uniquely identified by the index pair (k,l) in a slot,where k and l are indices in the frequency and time domainsrespectively. While uplink subframes in one component carrier (CC) arediscussed herein, uplink subframes are defined for each CC.

FIG. 4 shows examples of several numerologies 401. The numerology #1 401a may be a basic numerology (e.g., a reference numerology). For example,a RE 495 a of the basic numerology 401 a may be defined with subcarrierspacing 405 a of 15 kHz in frequency domain and 2048 Ts+CP length (e.g.,160 Ts or 144 Ts) in time domain (i.e., symbol length #1 403 a), whereTs denotes a baseband sampling time unit defined as 1/(15000*2048)seconds. For the i-th numerology, the subcarrier spacing 405 may beequal to 15*2^(i) and the effective OFDM symbol length 2048*2^(−i)*Ts.It may cause the symbol length is 2048*2^(−i)*Ts+CP length (e.g.,160*2^(−i)*Ts or 144*2^(−i)*Ts). In other words, the subcarrier spacingof the i+1-th numerology is a double of the one for the i-th numerology,and the symbol length of the i+1-th numerology is a half of the one forthe i-th numerology. FIG. 4 shows four numerologies, but the system maysupport another number of numerologies. Furthermore, the system does nothave to support all of the 0-th to the I-th numerologies, i=0, 1, . . ., I.

FIG. 5 shows examples of subframe structures for the numerologies 501that are shown in FIG. 4. Given that a slot 283 includes N^(DL) _(symb)(or N^(UL) _(symb))=7 symbols, the slot length of the i+1-th numerology501 is a half of the one for the i-th numerology 501, and eventually thenumber of slots 283 in a subframe (i.e., 1 ms) becomes double. It may benoted that a radio frame may include 10 subframes, and the radio framelength may be equal to 10 ms.

FIG. 6 shows examples of slots 683 and sub-slots 607. If a sub-slot 607is not configured by higher layer, the UE 102 and the eNB/gNB 160 mayonly use a slot 683 as a scheduling unit. More specifically, a giventransport block may be allocated to a slot 683. If the sub-slot 607 isconfigured by higher layer, the UE 102 and the eNB/gNB 160 may use thesub-slot 607 as well as the slot 683. The sub-slot 607 may include oneor more OFDM symbols. The maximum number of OFDM symbols that constitutethe sub-slot 607 may be N^(DL) _(symb)−1 (or N^(UL) _(symb)−1).

The sub-slot length may be configured by higher layer signaling.Alternatively, the sub-slot length may be indicated by a physical layercontrol channel (e.g., by DCI format).

The sub-slot 607 may start at any symbol within a slot 683 unless itcollides with a control channel. There could be restrictions ofmini-slot length based on restrictions on starting position. Forexample, the sub-slot 607 with the length of N^(DL) _(symb)−1 (or N^(UL)_(symb)−1) may start at the second symbol in a slot 683. The startingposition of a sub-slot 607 may be indicated by a physical layer controlchannel (e.g., by DCI format). Alternatively, the starting position of asub-slot 607 may be derived from information (e.g., search space index,blind decoding candidate index, frequency and/or time resource indices,PRB index, a control channel element index, control channel elementaggregation level, an antenna port index, etc.) of the physical layercontrol channel which schedules the data in the concerned sub-slot 607.

In cases when the sub-slot 607 is configured, a given transport blockmay be allocated to either a slot 683, a sub-slot 607, aggregatedsub-slots 607 or aggregated sub-slot(s) 607 and slot 683. This unit mayalso be a unit for HARQ-ACK bit generation.

FIG. 7 shows examples of scheduling timelines 709. For a normal DLscheduling timeline 709 a, DL control channels are mapped the initialpart of a slot 783 a. The DL control channels 711 schedule DL sharedchannels 713 a in the same slot 783 a. HARQ-ACKs for the DL sharedchannels 713 a (i.e., HARQ-ACKs each of which indicates whether or nottransport block in each DL shared channel 713 a is detectedsuccessfully) are reported via UL control channels 715 a in a later slot783 b. In this instance, a given slot 783 may contain either one of DLtransmission and UL transmission.

For a normal UL scheduling timeline 709 b, DL control channels 711 b aremapped the initial part of a slot 783 c. The DL control channels 711 bschedule UL shared channels 717 a in a later slot 783 d. For thesecases, the association timing (time shift) between the DL slot 783 c andthe UL slot 783 d may be fixed or configured by higher layer signaling.Alternatively, it may be indicated by a physical layer control channel(e.g., the DL assignment DCI format, the UL grant DCI format, or anotherDCI format such as UE-common signaling DCI format which may be monitoredin common search space).

For a self-contained base DL scheduling timeline 709 c, DL controlchannels 711 c are mapped to the initial part of a slot 783 e. The DLcontrol channels 711 c schedule DL shared channels 713 b in the sameslot 783 e. HARQ-ACKs for the DL shared channels 713 b are reported inUL control channels 715 b, which are mapped at the ending part of theslot 783 e.

For a self-contained base UL scheduling timeline 709 d, DL controlchannels 711 d are mapped to the initial part of a slot 783 f. The DLcontrol channels 711 d schedule UL shared channels 717 b in the sameslot 783 f. For these cases, the slot 783 f may contain DL and ULportions, and there may be a guard period between the DL and ULtransmissions.

The use of a self-contained slot may be upon a configuration ofself-contained slot. Alternatively, the use of a self-contained slot maybe upon a configuration of the sub-slot. Yet alternatively, the use of aself-contained slot may be upon a configuration of shortened physicalchannel (e.g., PDSCH, PUSCH, PUCCH, etc.).

FIG. 8 shows examples of DL control channel monitoring regions. One ormore sets of PRB(s) may be configured for DL control channel monitoring.In other words, a control resource set is, in the frequency domain, aset of PRBs within which the UE 102 attempts to blindly decode downlinkcontrol information, where the PRBs may or may not be frequencycontiguous, a UE 102 may have one or more control resource sets, and oneDCI message may be located within one control resource set. In thefrequency-domain, a PRB is the resource unit size (which may or may notinclude DMRS) for a control channel. A DL shared channel may start at alater OFDM symbol than the one(s) which carries the detected DL controlchannel. Alternatively, the DL shared channel may start at (or earlierthan) an OFDM symbol than the last OFDM symbol which carries thedetected DL control channel. In other words, dynamic reuse of at leastpart of resources in the control resource sets for data for the same ora different UE 102, at least in the frequency domain may be supported.

FIG. 9 shows examples of DL control channel which consists of more thanone control channel elements. When the control resource set spansmultiple OFDM symbols, a control channel candidate may be mapped tomultiple OFDM symbols or may be mapped to a single OFDM symbol. One DLcontrol channel element may be mapped on REs defined by a single PRB anda single OFDM symbol. If more than one DL control channel elements areused for a single DL control channel transmission, DL control channelelement aggregation may be performed.

The number of aggregated DL control channel elements is referred to asDL control channel element aggregation level. The DL control channelelement aggregation level may be 1 or 2 to the power of an integer. ThegNB 160 may inform a UE 102 of which control channel candidates aremapped to each subset of OFDM symbols in the control resource set. Ifone DL control channel is mapped to a single OFDM symbol and does notspan multiple OFDM symbols, the DL control channel element aggregationis performed within an OFDM symbol, namely multiple DL control channelelements within an OFDM symbol are aggregated. Otherwise, DL controlchannel elements in different OFDM symbols can be aggregated.

FIG. 10 shows examples of UL control channel structures. UL controlchannel may be mapped on REs which are defined a PRB and a slot infrequency and time domains, respectively. This UL control channel may bereferred to as a long format (or just the 1st format). UL controlchannels may be mapped on REs on a limited OFDM symbols in time domain.This may be referred to as a short format (or just the 2nd format). TheUL control channels with a short format may be mapped on REs within asingle PRB. Alternatively, the UL control channels with a short formatmay be mapped on REs within multiple PRBs. For example, interlacedmapping may be applied, namely the UL control channel may be mapped toevery N PRBs (e.g. 5 or 10) within a system bandwidth.

FIG. 11 is a block diagram illustrating one implementation of an gNB1160. The gNB 1160 may include a higher layer processor 1123, a DLtransmitter 1125, a UL receiver 1133, and one or more antenna 1131. TheDL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCHtransmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135and a PUSCH receiver 1137.

The higher layer processor 1123 may manage physical layer's behaviors(the DL transmitter's and the UL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1123 may obtain transport blocks from the physical layer. Thehigher layer processor 1123 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1123 may provide the PDSCH transmitter transportblocks and provide the PDCCH transmitter transmission parameters relatedto the transport blocks.

The DL transmitter 1125 may multiplex downlink physical channels anddownlink physical signals (including reservation signal) and transmitthem via transmission antennas 1131. The UL receiver 1133 may receivemultiplexed uplink physical channels and uplink physical signals viareceiving antennas 1131 and de-multiplex them. The PUCCH receiver 1135may provide the higher layer processor 1123 UCI. The PUSCH receiver 1137may provide the higher layer processor 1123 received transport blocks.

FIG. 12 is a block diagram illustrating one implementation of a UE 1202.The UE 1202 may include a higher layer processor 1223, a UL transmitter1251, a DL receiver 1243, and one or more antenna 1231. The ULtransmitter 1251 may include a PUCCH transmitter 1253 and a PUSCHtransmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245and a PDSCH receiver 1247.

The higher layer processor 1223 may manage physical layer's behaviors(the UL transmitter's and the DL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1223 may obtain transport blocks from the physical layer. Thehigher layer processor 1223 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1223 may provide the PUSCH transmitter transportblocks and provide the PUCCH transmitter 1253 UCI.

The DL receiver 1243 may receive multiplexed downlink physical channelsand downlink physical signals via receiving antennas 1231 andde-multiplex them. The PDCCH receiver 1245 may provide the higher layerprocessor 1223 DCI. The PDSCH receiver 1247 may provide the higher layerprocessor 1223 received transport blocks.

It should be noted that names of physical channels described herein areexamples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH andNRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or thelike can be used.

FIG. 13 illustrates examples of short PUCCH formats. A first example (a)is a frequency division multiplexing (FDM) case. A short PUCCH formatmay occupy only 1 symbol length. In this case, CP-OFDM modulation shouldbe used, the reference symbols (e.g., DMRS) and UCI carrying symbols canbe multiplexed in different subcarriers of a PUCCH resource.

A second example (b) is a time division multiplexing (TDM) case. Theshort PUCCH format occupies two symbols. In this case, both CP-OFDM andDFT-S-OFDM modulation can be used. In case of DFT-S-OFDM, referencesymbol (e.g., DMRS) and the UCI carrying symbol can be TDM multiplexed.

A third example (c) is a TDM with symbol splitting case. The short PUCCHoccupies 1 symbol of reference numerology by splitting it into 2 symbolswith a higher numerology (i.e., double the subcarrier spacing and reducethe symbol length by half). In this case, the PUCCH includes a referencesymbol (e.g., DMRS) component and a UCI component. This 1-symbol designis actually a 2-symbol design with a higher numerology, and the samedesign as 2-symbol PUCCH can be used.

FIG. 14 illustrates examples of reference symbol (RS) patterns for PUCCHin an Orthogonal Frequency Division Multiplexing (OFDM) symbol. FIG. 14shows the reference signal pattern designs for 2 RS in each RB, 3 RS ineach RB, 4 RS in each RB, and 6 RS in each RB.

FIG. 15 illustrates an example of demodulation reference signal (DMRS)multiplexing with frequency division multiplexing (FDM) for a 1-symbolshort PUCCH. FIG. 15 shows RS multiplexing of 2 UEs 102 with differentRS patterns. Orthogonal sequences can still be applied on the REscarrying coded UCI data. The RS for a first UE (UE1) are multiplexedwith the RS for a second UE (UE2).

FIG. 16 illustrates an example of RS location in a 2-symbol short PUCCHwith a discrete Fourier transform spread OFDM (DFT-S-OFDM). In a firstmethod (a), the first symbol is always DMRS, and the second symbol isalways for UCI data. The DMRS is transmitted first so that the basestation (gNB 160) can decode earlier compared with a post-loaded DMRS.However, if different UEs 102 start short PUCCH at different symbols,the DMRS pattern of one UE 102 may collide with the UCI data part ofanother UE 102. This may cause interference to the Z-C sequence used forDMRS.

In a second method (b), to avoid interference due to RS misalignmentamong UEs 102, the location of the DMRS may be fixed in certain symbollocations. For example, a symbol with odd symbol index is used for DMRS,a symbol with even symbol index is used for UCI data, or vice versa.Therefore, depending on the starting symbol of a 2-symbol short PUCCH,the DMRS location may be in the first symbol of second symbol of a2-symbol PUCCH.

In a third method (not shown), the RS location is changeable orconfigurable. The RS location within a 2-symbol PUCCH can besemi-statically configured by higher layer signaling for a given UE 102.The RS location within a 2-symbol PUCCH can be dynamically indicated bya DCI. The adjustable RS location can be used to avoid interference dueto RS misalignment among different UEs 102.

FIG. 17 illustrates examples of RS pattern determination. In oneapproach (a), a fixed RS pattern in always applied. For example with 3RS in a RB, pattern 1 is always applied. In another approach (b), the RSpattern is determined based on the symbol index of the starting symbol.For example, with 3 RS in a RB, pattern 1 is used if the starting symbolhas an even index number, and pattern 2 is used if the starting symbolhas an odd index number, or vice versa. In yet another approach (notshown), the RS pattern can be changeable or configurable. The RS patterncan be semi-statically configured by higher layer signaling ordynamically indicated by a DCI for a given UE 102.

FIG. 18 illustrates examples of RS located in two symbols. In oneapproach (a), the same RS pattern is applied to both symbols. The RSpattern can be fixed, or semi-statically configured by higher layersignaling, or dynamically indicated by a DCI for a given UE 102. Inanother approach (b), different RS patterns are used in differentsymbols. An interlaced pattern is used in different symbols. The RSpattern on a symbol may be configured semi-statically. The RS pattern ona symbol may be indicated by a based station via a DCI. The RS patternmay be determined based on the symbol index of the given symbol (e.g.,pattern 1 is used for symbol with even index number, and pattern 2 isused for symbol with odd index number, or vice versa).

FIG. 19 illustrates examples of RS multiplexing of two UEs withdifferent RS patterns. Orthogonal sequences can still be applied on theREs carrying coded UCI data. In one approach (a), the RS multiplexing ofdifferent UEs may be allocated in the same symbol. In another approach(b), the RS multiplexing of different UEs may be allocated in differentsymbols.

FIG. 20 illustrates examples of short PUCCH transmission with beamsweeping. In a first approach (a), a 1-symbol short PUCCH can betransmitted in any one of the configured PUCCH symbols. In a secondapproach (b), a 2-symbol short PUCCH can be transmitted on any twoconsecutive symbols within the configured PUCCH symbols. In a thirdapproach (c), a 2-symbol short PUCCH can be transmitted in any twosymbols within the configured PUCCH symbols.

FIG. 21 illustrates various components that may be utilized in a UE2102. The UE 2102 described in connection with FIG. 21 may beimplemented in accordance with the UE 102 described in connection withFIG. 1. The UE 2102 includes a processor 2103 that controls operation ofthe UE 2102. The processor 2103 may also be referred to as a centralprocessing unit (CPU). Memory 2105, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 2107 a anddata 2109 a to the processor 2103. A portion of the memory 2105 may alsoinclude non-volatile random access memory (NVRAM). Instructions 2107 band data 2109 b may also reside in the processor 2103. Instructions 2107b and/or data 2109 b loaded into the processor 2103 may also includeinstructions 2107 a and/or data 2109 a from memory 2105 that were loadedfor execution or processing by the processor 2103. The instructions 2107b may be executed by the processor 2103 to implement the methodsdescribed above.

The UE 2102 may also include a housing that contains one or moretransmitters 2158 and one or more receivers 2120 to allow transmissionand reception of data. The transmitter(s) 2158 and receiver(s) 2120 maybe combined into one or more transceivers 2118. One or more antennas2122 a-n are attached to the housing and electrically coupled to thetransceiver 2118.

The various components of the UE 2102 are coupled together by a bussystem 2111, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 21 as the bus system2111. The UE 2102 may also include a digital signal processor (DSP) 2113for use in processing signals. The UE 2102 may also include acommunications interface 2115 that provides user access to the functionsof the UE 2102. The UE 2102 illustrated in FIG. 21 is a functional blockdiagram rather than a listing of specific components.

FIG. 22 illustrates various components that may be utilized in a gNB2260. The gNB 2260 described in connection with FIG. 22 may beimplemented in accordance with the gNB 160 described in connection withFIG. 1. The gNB 2260 includes a processor 2203 that controls operationof the gNB 2260. The processor 2203 may also be referred to as a centralprocessing unit (CPU). Memory 2205, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 2207 a anddata 2209 a to the processor 2203. A portion of the memory 2205 may alsoinclude non-volatile random access memory (NVRAM). Instructions 2207 band data 2209 b may also reside in the processor 2203. Instructions 2207b and/or data 2209 b loaded into the processor 2203 may also includeinstructions 2207 a and/or data 2209 a from memory 2205 that were loadedfor execution or processing by the processor 2203. The instructions 2207b may be executed by the processor 2203 to implement the methodsdescribed above.

The gNB 2260 may also include a housing that contains one or moretransmitters 2217 and one or more receivers 2278 to allow transmissionand reception of data. The transmitter(s) 2217 and receiver(s) 2278 maybe combined into one or more transceivers 2276. One or more antennas2280 a-n are attached to the housing and electrically coupled to thetransceiver 2276.

The various components of the gNB 2260 are coupled together by a bussystem 2211, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 22 as the bus system2211. The gNB 2260 may also include a digital signal processor (DSP)2213 for use in processing signals. The gNB 2260 may also include acommunications interface 2215 that provides user access to the functionsof the gNB 2260. The gNB 2260 illustrated in FIG. 22 is a functionalblock diagram rather than a listing of specific components.

FIG. 23 is a block diagram illustrating one implementation of a UE 2302in which systems and methods for a short PUCCH design for 5G NRoperations may be implemented. The UE 2302 includes transmit means 2358,receive means 2320 and control means 2324. The transmit means 2358,receive means 2320 and control means 2324 may be configured to performone or more of the functions described in connection with FIG. 1 above.FIG. 21 above illustrates one example of a concrete apparatus structureof FIG. 23. Other various structures may be implemented to realize oneor more of the functions of FIG. 1. For example, a DSP may be realizedby software.

FIG. 24 is a block diagram illustrating one implementation of a gNB 2460in which systems and methods for a short PUCCH design for 5G NRoperations may be implemented. The gNB 2460 includes transmit means2417, receive means 2478 and control means 2482. The transmit means2417, receive means 2478 and control means 2482 may be configured toperform one or more of the functions described in connection with FIG. 1above. FIG. 22 above illustrates one example of a concrete apparatusstructure of FIG. 24. Other various structures may be implemented torealize one or more of the functions of FIG. 1. For example, a DSP maybe realized by software.

FIG. 25 is a flow diagram illustrating a method 2500 for implementing ashort PUCCH design for 5G NR. The method 2500 may be implemented by a UE102. The UE 102 may determine 2502 the uplink control channel (PUCCH)format and configuration based on a signaling from a gNB 160. Forexample, the PUCCH format and configuration may include at least a shortPUCCH format and a long PUCCH format. The short PUCCH format and longPUCCH format may have the same or different waveforms and/ornumerologies.

A short PUCCH may be a 1-symbol short PUCCH. A 1-symbol short PUCCH mayemploy a cyclic prefix Orthogonal Frequency Division Multiplexing(CP-OFDM) waveform. A format may consist of a number of resource blocks(RBs), a reference symbol (RS) pattern, and/or orthogonal sequences onRS and data symbols, and/or one or more control resource regions. The RSpattern of different UEs 102 may be multiplexed with an orthogonalsequence or in a frequency division multiplexing (FDM) manner.

A short PUCCH may be a 2-symbol short PUCCH. A 2-symbol short PUCCH mayemploy a discrete Fourier transform spread OFDM (DFT-S-OFDM) waveform. Aformat may consist of a number of RBs, a RS location, and/or orthogonalsequences on RS and data symbols, and/or one or more control resourceregions. Alternatively, a 2-symbol short PUCCH may employ a CP-OFDMwaveform, and a format consists of a number of RBs, a RS pattern andlocation, and/or orthogonal sequences on RS and data symbols, and/or oneor more control resource regions.

The RS location may be the first symbol of the 2-symbol short PUCCH. TheRS location may be determined by the symbol index of a 2-symbol shortPUCCH. The RS location of the 2-symbol short PUCCH may be indicated bygNB signaling.

At least for a frequency band over 6 GHz, a UE 102 may be configuredwith a set of symbols for a short PUCCH, and a short PUCCH istransmitted by selecting one symbol for a 1-symbol PUCCH and 2 symbolsfor a 2-symbol PUCCH within the set. The 2 symbols selected for the2-symbol PUCCH within the set can be contiguous or separated within theset. The symbol(s) may be selected based on a gNB indication.

The UE 102 may determine 2504 the control channel used for uplinkcontrol information (UCI) feedback. The UE 102 may determine 2506 theresource of the control channel for UCI feedback. The UE 102 maytransmit 2508 UCI on the selected channel.

FIG. 26 is a flow diagram illustrating another method 2600 forimplementing a short PUCCH design for 5G NR. The method 2600 may beimplemented by a base station (gNB) 160. The gNB 160 may determine 2602the uplink control channel (PUCCH) format and configuration. This may beaccomplished as described in connection with FIG. 27. For example, thePUCCH format and configuration may include at least a short PUCCH formatand a long PUCCH format. The short PUCCH format and long PUCCH formatmay have the same or different waveforms and/or numerologies.

The gNB 160 may receive 2604 UCI on a selected channel. A controlchannel used for uplink control information (UCI) feedback and aresource of the control channel for UCI feedback may be determined by aUE 102 based on signaling from the gNB 160.

FIG. 27 is a flow diagram illustrating another method 2700 forimplementing a short PUCCH design for 5G NR. The method 2700 may beimplemented by a UE 102.

The UE 102 may acquire 2702 a first higher layer configurationindicating at least a short uplink control channel (PUCCH) resourceconfiguration. The first higher layer configuration may include at leasta number of symbols, a number of resource blocks (RBs), and whetherfrequency hopping is applied in a case of a short PUCCH with twosymbols. In the case of the short PUCCH with two symbols, referencesignal (RS) locations on the two symbols may be the same. The RSlocations may be resource elements indexed with {1,4,7,10}.

The UE 102 may acquire 2704 a second higher layer configurationindicating multiple sets of PUCCH resource configurations. One set ofPUCCH resource configurations within the multiple sets of PUCCH resourceconfigurations may include the short PUCCH resource configuration.

The UE 102 may select 2706 a set of PUCCH resource configurations fromthe sets of PUCCH resource configurations based on a payload size ofuplink control information (UCI).

The UE 102 may transmit 2708 the UCI on a PUCCH resource, the PUCCHresource corresponding to a PUCCH resource configuration within theselected set of PUCCH resource configurations.

FIG. 28 is a flow diagram illustrating another method 2800 forimplementing a short PUCCH design for 5G NR. The method 2800 may beimplemented by a base station (gNB) 160.

The gNB 160 may send 2802 a first higher layer configuration indicatingat least a short uplink control channel (PUCCH) resource configuration.The first higher layer configuration may include at least a number ofsymbols, a number of resource blocks (RBs), and whether frequencyhopping is applied in a case of a short PUCCH with two symbols. In thecase of the short PUCCH with two symbols, reference signal (RS)locations on the two symbols may be the same. The RS locations may beresource elements indexed with {1,4,7,10}.

The gNB 160 may send 2804 a second higher layer configuration indicatingmultiple sets of PUCCH resource configurations, one set of PUCCHresource configurations within the multiple sets of PUCCH resourceconfigurations include the short PUCCH resource configuration.

The gNB 160 may select 2806 a set of PUCCH resource configurations fromthe sets of PUCCH resource configurations based on a payload size ofuplink control information (UCI).

The gNB 160 may receive 2808 the UCI on a PUCCH resource, the PUCCHresource corresponding to a PUCCH resource configuration within theselected set of PUCCH resource configurations

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or a processor. The term“computer-readable medium,” as used herein, may denote a computer-and/or processor-readable medium that is non-transitory and tangible. Byway of example, and not limitation, a computer-readable orprocessor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer or processor. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray® disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein maybe implemented in and/or performed using hardware. For example, one ormore of the methods described herein may be implemented in and/orrealized using a chipset, an application-specific integrated circuit(ASIC), a large-scale integrated circuit (LSI) or integrated circuit,etc.

Each of the methods disclosed herein comprises one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD, and the like), a magneticstorage medium (for example, a magnetic tape, a flexible disk, and thelike), and the like, any one may be possible. Furthermore, in somecases, the function according to the described systems and methodsdescribed above is realized by running the loaded program, and inaddition, the function according to the described systems and methods isrealized in conjunction with an operating system or other applicationprograms, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedabove may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedembodiments may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may comprise a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller or a state machine. The general-purpose processor oreach circuit described above may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

What is claimed is:
 1. A user equipment (UE), comprising: a processor;and memory in electronic communication with the processor, whereininstructions stored in the memory are executable to: acquire a firsthigher layer configuration indicating at least a physical uplink controlchannel (PUCCH) resource configuration corresponding to a PUCCH formatamong a plurality of PUCCH formats which have at least two types oflengths, wherein the PUCCH format consists of one or two symbol(s);acquire a second higher layer configuration indicating multiple sets ofPUCCH resource configurations; select a set of PUCCH resourceconfigurations from the sets of PUCCH resource configurations based on apayload size of uplink control information (UCI); and transmit the UCIon a PUCCH resource, the PUCCH resource corresponding to a PUCCHresource configuration within the selected set of PUCCH resourceconfigurations.
 2. The UE of claim 1, wherein the first higher layerconfiguration comprises at least a number of symbols and a number ofresource blocks (RBs).
 3. The UE of claim 1, wherein, in a case wherethe PUCCH format consists of two symbols, reference signal (RS)locations on the two symbols are the same.
 4. The UE of claim 3, the RSlocations are resource elements indexed with {1,4,7,10}.
 5. A basestation, comprising: a processor; and memory in electronic communicationwith the processor, wherein instructions stored in the memory areexecutable to: send a first higher layer configuration indicating atleast a physical uplink control channel (PUCCH) resource configurationcorresponding to a PUCCH format among a plurality of PUCCH formats whichhave at least two types of lengths, wherein the PUCCH format consists ofone or two symbol(s); send a second higher layer configurationindicating multiple sets of PUCCH resource configurations; and receiveuplink control information (UCI) on a PUCCH resource, the PUCCH resourcecorresponding to a PUCCH resource configuration within a set of PUCCHresource configurations selected from the sets of PUCCH resourceconfigurations based on a payload size of the UCI.
 6. The base stationof claim 5, wherein the first higher layer configuration comprises atleast a number of symbols and a number of resource blocks (RBs).
 7. Thebase station of claim 5, wherein, in a case where the PUCCH formatconsists of two symbols, reference signal (RS) locations on the twosymbols are the same.
 8. The base station of claim 7, the RS locationsare resource elements indexed with {1,4,7,10}.
 9. A method for a userequipment (UE), the method comprising: acquiring a first higher layerconfiguration indicating at least a physical uplink control channel(PUCCH) resource configuration corresponding to a PUCCH format among aplurality of PUCCH formats which have at least two types of lengths,wherein the PUCCH format consists of one or two symbol(s); acquiring asecond higher layer configuration indicating multiple sets of PUCCHresource configurations; selecting a set of PUCCH resourceconfigurations from the sets of PUCCH resource configurations based on apayload size of uplink control information (UCI); and transmitting theUCI on a PUCCH resource, the PUCCH resource corresponding to a PUCCHresource configuration within the selected set of PUCCH resourceconfigurations.
 10. A method for a base station, the method comprising:sending a first higher layer configuration indicating at least aphysical uplink control channel (PUCCH) resource configurationcorresponding to a PUCCH format among a plurality of PUCCH formats whichhave at least two types of lengths, wherein the PUCCH format consists ofone or two symbol(s); sending a second higher layer configurationindicating multiple sets of PUCCH resource configurations; and receivinguplink control information (UCI) on a PUCCH resource, the PUCCH resourcecorresponding to a PUCCH resource configuration within a set of PUCCHresource configurations selected from the sets of PUCCH resourceconfigurations based on a payload size of the UCI.